Logging and profiling content space data and coverage metric self-reporting

ABSTRACT

A computer-implemented method for generating user stories for a software product, includes collecting, by a processor, a plurality of requirements, creating, by the processor, a plurality of content space specification files that includes the plurality of requirements, processing, by the processor, the plurality of content space specification files to generate the user stories that are related to real time data of the software product, defining, by the processor, a content space, mapping, by the processor, the user stories to the content space and embedding, by the processor, the content space with the software product, wherein user stories include at least one of real time log data, profile statistics data, and coverage metric self-reporting data.

DOMESTIC PRIORITY

This application is a continuation application of the legally relatedU.S. Ser. No. 13/741,788 filed Jan. 15, 2013, the contents of which areincorporated by reference herein in their entirety.

BACKGROUND

The present invention relates to software development, and morespecifically, to systems and methods for logging and profiling contentspace data and self-reporting for coverage metrics into a softwareproduct for use at run-time of the software product.

As part of developing products and applications, particularly softwareproducts and applications, requirements are determined, usually from awide variety of sources, such as stake-holders, strategy people,customers, marketing, industry trends, standards organizations, andmore. Through various channels, a detailed technical plan of activitiesfor the software development team is derived from the requirements,which can interact in complex ways. The process of generating detailedimplementation plans from requirements is subject to errors from varioussources. Multiple concurrent dialogs among teams, making assumptions anddecisions in parallel, can propagate errors, which can become built intothe project plans and the product architecture and or designs. As such,business results such as time to market, development cost, productviability to compete in the marketplace, and the like can affected.

Use cases (user stories) have long been implemented to organize anditemize requirements for software products or application software. Usecases bridge the gap between business and market knowledge, and systemdesign, by focusing on the user interactions with the system. Thebreakdown of requirements into use case or line items frequently occursin parallel with, and is in dialog with, the architects and designleaders. During the time frame that requirements are collected andanalyzed, the requirements are subject to change which must be reflectedin the line items or use cases. In addition, new requirements arebrought up and must be analyzed and fit with the existing line items oruse cases. Some requirements are eliminated, with corresponding impactson line items or use cases.

User stories can be a basis for development sprint planning and statustracking, and the basis for a key functional verification test (FVT)quality metric call ‘content coverage’. Several usage scenarios can bepresented in user story form. For example, product owners are interestedin what user stories are being executed the most in the field, so thatthey can focus usability enhancements to those stories. Developmenttechnical leaders are interested in what user stories are taking themost time in the field (i.e., time per story multiplied by executionfrequency), so that they can focus performance improvements on thosestories and deliver measurable dollar-value to customers. Projectmanagers are interested in what user stories are encountering defectsthe most in the field (i.e., defects per story multiplied by executionfrequency), so that they can focus quality improvements on thosestories. Test leads are interested in what user stories are getting goodcoverage in the field, so they can prioritize my testing on the lessused stories. Lead IT are interested in what user stories are being usedmost, and how long they are cumulatively taking, so that they canmonitor how the time of the IT Staff is being spent. FVT leads areinterested in the content coverage metric with splits by platform, byinterface and so on, that is reliable and highly automated so my testengineers don't have to spend time collecting the data for dashboards.

SUMMARY

Exemplary embodiments include a computer-implemented method forgenerating user stories for a software product, the method includingcollecting, by a processor, a plurality of requirements, creating, bythe processor, a plurality of content space specification files thatincludes the plurality of requirements, processing, by the processor,the plurality of content space specification files to generate the userstories that are related to real time data of the software product,defining, by the processor, a content space, mapping, by the processor,the user stories to the content space and embedding, by the processor,the content space with the software product, wherein user storiesinclude at least one of real time log data, profile statistics data, andcoverage metric self-reporting data.

Additional exemplary embodiments include a computer program product forgenerating user stories for a software product, the computer programproduct including a computer readable medium storing instructions forcausing a computer to implement a method. The method includescollecting, by a processor, a plurality of requirements, creating, bythe processor, a plurality of content space specification files thatincludes the plurality of requirements, processing, by the processor,the plurality of content space specification files to generate the userstories that are related to real time data of the software product,defining, by the processor, a content space, mapping, by the processor,the user stories to the content space and embedding, by the processor,the content space with the software product, wherein user storiesinclude at least one of real time log data, profile statistics data, andcoverage metric self-reporting data.

Further exemplary embodiments include a computer-implemented method forgenerating user stories for a software product, the method includingcollecting a plurality of requirements, defining a content spaceincluding a plurality of cells, each cell defining an agile story, eachcell having a plurality of dimensions, creating a plurality of contentspace specification files that includes the plurality of requirements,defining a content space, traversing at least one dimension of each ofthe plurality of cells to generate a user story related to real timedata of the software product, mapping the user story to the contentspace, embedding the content space with the software product andgenerating reports defining the user story, wherein user story includesat least one of real time log data, profile statistics data, andcoverage metric self-reporting data

Additional features and advantages are realized through the techniquesof the present invention. Other embodiments and aspects of the inventionare described in detail herein and are considered a part of the claimedinvention. For a better understanding of the invention with theadvantages and the features, refer to the description and to thedrawings.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The subject matter which is regarded as the invention is particularlypointed out and distinctly claimed in the claims at the conclusion ofthe specification. The forgoing and other features, and advantages ofthe invention are apparent from the following detailed description takenin conjunction with the accompanying drawings in which:

FIG. 1 illustrates a high level block diagram of a system for generatingagile user stories into a content space, which then is implemented forlogging and profiling content space data and coverage metricself-reporting;

FIG. 2 illustrates a chart representation of the five exemplarydimensions described herein;

FIG. 3 illustrates the system for logging and profiling content spacedata and coverage metric self-reporting of FIG. 1, further illustratingthe content space tool process flow that defines implementation ofcontent space data;

FIG. 4 illustrates a screen shot of a graphical user interface (GUI)that can be implemented by a user to view and navigate content spacedata as described herein.

FIG. 5 illustrates an exemplary embodiment of a system in which contentspace logging and profiling and coverage metric self-reporting can beimplemented.

DETAILED DESCRIPTION

In exemplary embodiments, the systems and methods described hereingenerate user stories that facilitate moving user story information inlogs and error messages to be used by customers and analysis, and movingprofile information for customer review. In exemplary embodiments, thesystems and methods described herein provide administrative tools tomonitor and visualize user story data for usage of a software product.The administrator can pass the data on to a particular company forinclusion in the agile process without confidentiality concerns. Inexemplary embodiments, the saved user story data can be in a formincluding but not limited to: a log file; a database and files.Regardless of the form, each form includes timestamps or intervalmeasurements, so that users can analyze not only the frequency of eachstory, but also the mean time or cumulative time for each story.

In exemplary embodiments, the systems and methods described hereininclude an internal representation of a software product's own userstories (generated via a content space) with interfaces for internalaccess. The internal representation ships with the software product.When there is an error log entry associated with the software product,an error message or first-failure data capture (FFDC) data is to begenerated, and the content space coordinates for user stories relevant,are included with log or message data. The user story data is thenincluded in the content space when it is sent to the respective company.In exemplary embodiments, this data is included in defects, asappropriate, for later analysis. In addition, for any given log entry,message, and the like, multiple user stories may be relevant and aresupported in the content space.

In exemplary embodiments, the system and methods described hereinsupport profiling by collecting execution counts and duration data asexecution occurs in the customer installation. This data is saved withassociated indexes to map it to user stories. In addition, customers areprovided with tools (e.g., user interfaces) to view and perhaps exportthis data, and request and view analysis.

In exemplary embodiments, the systems and methods described hereinsupport content coverage metrics by tools to reset parts of the profiledata and extract (perhaps via command line interface (CLI)) the basedata after tests have been executed. The exported data allows directcalculation of content coverage metrics with necessary splits.

As described herein, a content space model is implemented for not onlycollecting requirements and generating user stories but also for loggingand profiling content space data and coverage metric self-reporting fora software product. A content space is a way of representing softwarecontent from an outside-in perspective via a set of dimensions. Each ofthe content space dimensions has values defined in terms of the softwareitself that concern a particular aspect, such as informationabstraction, function, external interface and run-time environment. Thedimension values can represent existing content and also new content forthe software, based on requirements (via content space analysis) for anew release. The content space can be programmatically traversed, and asthis traversal occurs, end-to-end testable units (termed user stories)are output, each corresponding to a particular region of the contentspace and having content space coordinates. The set of all output userstories partitions the software content and the set of all new andchanged user stories partitions the release requirements. The set of alluser stories and various subsets (e.g., all Power user stories) are usedto compute the content coverage metric of various scopes.

An example of how a content space can be set up and implemented is nowdiscussed. It will be appreciated that the following example isillustrative of a content space and not limiting.

In exemplary embodiments, the content space can be a five-dimensionalspace (termed either as a ‘software product content space’ or a ‘contentspace’), such that each cell within the content space is an end-to-enduse case (i.e., agile user story). In exemplary embodiments, the systemsand methods described herein can be implemented at various levels ofscale, from individual software components to very large productscomprising hundreds of components to include in the content space andfor logging and profiling content space data and coverage metricself-reporting for the software product. The five dimensions structurethe work as needed by software development (i.e., design, test, projectmanagement), and the requirements serve to define the values used on thedimensions. As such, the exemplary content space servers to bridge therequirements domain and implementation domain.

FIG. 1 illustrates a high level block diagram of a system 100 forgenerating agile user stories into a content space, which then isimplemented for logging and profiling content space data and coveragemetric self-reporting. The system 100 outlines and overviews theexemplary methods, the blocks for which are described further herein. Itwill be appreciated that each of the summary details described hereinincludes multiple users from each of the two domains, with multiplereviews. The order in which the individual steps are executed is notnecessarily serial. Changes in requirements or additional insightshappen during a later step can necessitate reworking the results from anearlier step.

In exemplary embodiments, content space specification files 105 aregenerated from the various sources in the requirements domain asdescribed herein. As described further herein, the content spacespecification files are generated from various requirements 101. Acontent space tool 110 receives the content specification files 105 toautomatically generate the agile user stories that can be stored in auser story storage medium 115. An additional storage medium 120 can beimplemented to store changes to the specification files 105, or anyother suitable output during the content space generation. Oncegenerated, the agile user stories can be output to any suitable projectmanagement or test management tool 125 implemented by the users in thedevelopment domain.

The system 100 includes several functions, including, but not limitedto: 1) articulating the content space; 2) classifying regions of thecontent space; 3) grouping the regions of the content space; 4)assigning priorities to use cases; and 5) loading the project managementtool 125.

In articulating the content space, requirements are analyzed in terms ofthe five content space dimensions. This analysis results in (withiteration and consensus building) a definition of values for each of thefive dimensions, which is represented in a form that can beprogrammatically processed. In articulating the content space, thesystems and methods described herein address whether all therequirements are represented in the content space, whether each contentspace dimension value is properly defined and agreed upon, and whetherall the dimension values are related to explicit, implicit or futurerequirements.

In classifying the regions of the content space, once the team issatisfied that the content space is defined (i.e., all dimension valuesknown, understood, and reasonably well-defined) and that it doesencompass all the requirements for a selected time-frame, the team nextdecides on how to classify regions of the content space. Throughautomated systems with team decisions, every cell in the content spaceis categorized in a variety of types, including, but not limited to: 1)does not apply to the product; 2) does apply to the product but for somefuture release; 3) is part of the product today (or from some priorrelease) and has no enhancements or changes; 4) is part of the producttoday and is enhanced or changed in some way; and 5) is a new or anenhanced function. The systems and methods described herein determinewhether each content space dimension value is classified, and reviews ofthe results determine correctness.

Following agreement on the content space and categorization of regions,the content space regions are then grouped. Subsets of the content spaceare grouped together into a size which is desirable for projectmanagement and the scale of the product and teams. This step appliesparticularly to the content space regions classified as unchanged andnew or enhanced (changed). The two extremes are: an entire content spacecan grouped into a single output project management work item; or, atthe other extreme, every single content space cell can be output as asingle project management line item. Essentially every possible groupingin between these extremes is also supported. Typically used are groupingall new and changed user stories for a particular platform or groupingspecific sub-variations of a verb.

In exemplary embodiments, there is flexibility in how these regions areselected and how they related to the content space cell classifications.The systems and methods described herein determine whether the groupingis correct and do the groupings properly reflect the tradeoff betweenproject management needs and technical visibility based onclassifications and complexity.

The grouping of content space cells into right sized project managementwork items mostly focused on a new function and an existing andunchanged function. The user (team) can programmatically select thegrouping of content space cells based on many considerations suchoverall content space size, product size, degree of technical difficultyof new function, team size, number of team, and the like. In exemplaryembodiments, individual content cells are use cases (with adjustablegranularity) and the groupings are user functions or user stories.

Based on the relative priorities of requirements, regions of the contentspace (subsets of use cases) are assigned priority values. These can beused to help focus review sessions to ensure the right higher prioritycontent is defined. When loaded into a project management application,the priorities can be used directly by development in agile sprint(iteration) planning. The output project management work items are input(e.g., ‘import’) for example, from the user story storage medium 115,into an appropriate project management tool 125.

As described herein, a content space can be defined by five dimensions.In exemplary embodiments, the five dimensions of the content space are,in order: release (time); noun; verb; interface; and platform. The threedimensions, verb, interface and platform, are orthogonal andnoun-specific. That is, an instance of these (e.g., a verb set, aninterface set and a platform set) is defined for each noun of interest.Nouns are the fourth dimension. The combination of a noun and itsassociated 3D space is termed a ‘noun space’. A set of noun spaces at agiven point in time (usually associated with product release) constitutethe definition of the content space for a particular release of aproduct (when the point in time is chosen on a release calendarboundary). Instances a product content space for multiple releasesrepresent the fifth dimension of content space: time.

For illustrative purposes, an example of a software product, ahypothetical browser-based email client is discussed for ease ofdiscussion. It will be appreciated that other products are contemplatedfor which logging and profiling content space data and coverage metricself-reporting can be implemented.

FIG. 2 illustrates a chart 200 representation of the five exemplarydimensions described herein. As described herein, the five dimensions ofthe content space are, from inner three to out-most: platform 201;interface 202; verb 203; noun 204; and release (time) 205. All of thevalues for the dimensions are derived from the product requirements,either explicit or implicit.

The platform dimension 201 is interpreted broadly to include thehardware, operating system, middle ware, hypervisor, and languageruntime in which the product executes. Generally, meaningful platformelements are determined by each product. As such, the entireprerequisite software stack and hardware is considered. Values of theplatform dimension 201 can include specific releases of each of theseplatform components as needed, or can be more generally specified. Forexample, a platform might be AIX 5.2 or just AIX. Alternatively, theplatform might be Firefox 3.6 or better, or just Firefox. Values caninclude as needed ancillary hardware for storage, networking, hardwaremanagement controllers, firmware, etc. for the full functional systemconfiguration.

The interface dimension 202 has values chosen to identify and separatethe kinds of interfaces that the subject software presents to externalentities; people, other software or hardware. The values can bespecified by type such as Graphical User Interface (GUI), command lineinterface (CLI), and so on. The values can include programmableinterfaces such as web services (e.g. REST) and APIs. Protocols can alsobe specified as values (e.g., IPv6 or MPI (Message Processing Interface)used in super-computing environments).

The verb dimension 203 includes values such as functions or operationsthat are supported by the subject software for a particular noun. Theoperations may be specified at varying levels of granularity, dependingupon the needs of a given set of requirements. For example ‘copy’ or‘create’ might be sufficient. More fine-grained values such ‘copy tolike repository’ and ‘copy to new folder’ can also be used. The decisiondepends on considerations like how new the function is, or how criticalthe different forms of copy are to the product stake-holders (those thatdefine requirements), or how technically difficult to implement.

The noun dimension 204 is an abstract entity presented to externals viathe interface(s). Most software for direct use by people has a number ofsuch abstractions that people manipulate via the functions (verbs)presented by the software. Example nouns for an email client caninclude, but are not limited to: inbox; inbox email; folder; and draftemail. As with values on the above dimensions, there is flexibility inhow coarse-grained or fine-grained the nouns are defined. The rightlevel of noun dimension granularity for a given product and givenrelease depends on the requirements.

The time dimension 205 values include natural values (i.e., discreteunits) which are the releases planned for the product. The content spacefor release n+1 can be various additions and changes relative to therelease n content space. These additions, enhancements and other changesaffect the release n content space by changing the values defined on thevarious dimensions. New nouns, new verbs, new platforms, can all beadded. Enhancements to exiting nouns and verbs are common and definedexplicitly in the n+1 content space.

Because of the way the dimensions are defined, each generated user storyis an end-to-end testable unit of function (sometimes termed ‘FVT-able’,where FVT=Function Verification Test). For example, for an “email”client each user story is a cell in the five-dimensional space withcoordinates of release, noun, verb, interface and platform. For example,“send an email on Firefox via GUI release n” is represented by a 5-tuple{release n, email, send, GUI, Firefox}, as shown in FIG. 2.

FIG. 3 illustrates the system 100 for logging and profiling contentspace data and coverage metric self-reporting of FIG. 1, furtherillustrating the content space tool 110 process flow that definesimplementation of content space data. In exemplary embodiments,parameters are collected from the content space specification files 105at block 305. In addition, any input files and content space symbols andfilters are also read into the content space tool 110. As such,following invocation and initialization of the content space tool 110,the content space specification file(s) 105 are read. In addition, thecontent space specification files 105 are parsed for correctness andvarious checks are run to help ensure consistency across the possiblymultiple files. This processing includes all the symbols and filters. Atblock 310, the content space is managed. In exemplary embodiments,grouping and folding are techniques to manage content space size. Thesize of a content space is naturally expressed as the number of userstories it contains, or will output if requested. For example, insoftware products, content space sizes in range of hundreds to tens ofthousands. Average sizes can be in the range of two thousand to twentythousand. Both folding and grouping can manage content space sizewithout eliminating (or hiding) detail that needs to be visible from theuser story output file(s) 115.

In grouping user stories, a set of user stories is represented in outputas a single user story. For example all the user stories for platformABC or for function XYZ might be represented by a single output userstory. Grouping does not change the size of a content space. Groupingallows the number of output user stories to be directly managed withouteliminating any details from the CS specification. There is no limit onthe size of a user story group. In exemplary embodiments, grouping iscontrolled by the user by filters in the content space specificationfile 105.

As filtering occurs, when a filter matches a user story and the filterhas any kind of grouping requested, save the user story is saved in abuffer associated with the filter. After all filtering and allnon-grouped user stories are output. The content space tool 110 loopsthrough all the filters that have any kind of grouping. For each filter,the content space tool 110 performs several steps. First, if a simple‘group’ is requested in the filter, the content space tool 110 generatesthe single grouping user story, summary field, description field, andthe like, and writes to output. The content space tool 110 thencontinues to the next filter. If a type of ‘group by’ is requested, thenfor each group by element (e.g., noun, verb, ifc, platform), the contentspace tool 110 builds subsets of the respective values on the dimensionfrom among the buffered user stories. The content space tool 110 thengenerates a single user story group for each cross-dimension subset,generates the description field that itemizes the subset of user storiesfor the group, and writes the user story group.

Folding also reduces the number of output user stories like grouping.But in contrast to grouping, folding reduces the size of the contentspace. Folding reduces the size of the content space by collecting somenumber of dimension element values into a single value (folding operateson the content space itself while grouping operates on user stories).The resulting single value is then used as a dimension element value inplace of the multiple collected values, thereby reducing the size of thecontent space. The single resulting value is termed a folding symbol(‘fold sym’).

As described herein, folding does not eliminate the details from thecontent space specification file. The values collected into a fold symremain in the content space specification file 105, and the folding doneby the fold sym can be toggled on or off. The value-folding can beswitched on and off for each of the noun, verb, interface and platformdimensions independently or all four dimensions together. Hence not onlyare the values still in the spec file, but the content space can also beprocessed again and user stories generated without folding or differentfolding, to see the detail. Folding can include both dimension foldingand value folding.

In exemplary embodiments, the content space tool 110 processes commandline parameters to determine what kinds of folding are requested. If nofold parameter, the content space tool 110 implements the defaultsetting for folding. As the content space specification files 105 areread, the content space tool 110 collects a list of all fold syms, andvalues for each. After all the noun spaces are read from input files,the content space tool 110 invokes a fold function. The content spacetool implements dimension folding first if requested. For each dimensionfor which folding is requested, the dimension is folded to “*” in eachnoun space. If value folding is requested for any dimensions that havenot been folded, the following steps are implemented. If noun valuefolding, the content space tool 110 folds the noun values by removingnouns in value list of a fold sym and replace with single instance ofthe fold sym. For each (remaining) noun space, for each relevantdimension, the content space tool 110 check each dimension value to seeif it is in the value list of a fold sym. If the noun is in the valuelist of the fold sym, then the content space tool 110 removes the valueand adds the fold sym (once only) to the dimension list. If folding hasbeen set off, the content space tool 110 takes no action. The contentspace by default is loaded in this mode. If fold request for the ‘all’or similar, the interface and platform dimensions are folded (as above)and the verb dimension is value-folded for all noun spaces are folded,and the noun dimension is value-folded.

Referring still to FIG. 3, at block 315, each user story is enumeratedin the content space and run through filters to classify and possiblyadd data. At block 320, the user story groups are generated and at block325 show requests and a summary are generated and can be stored in theoutput 120. At block 326, the content space is embedded in the softwareproduct as described herein. At block 330, the content space data islogged and profiled and coverage metrics are self-reported as describedfurther herein. The system 100 can include an output 122 to store thelog and error message profile outputs, which is part of the customerenvironment. In exemplary embodiments, block 330 occurs in the softwareproduct runtime. In addition, the embedding of the content space occursoutside of the content space tool 110. The embedding occurs as part ofthe build of the software product. In exemplary embodiments, the system100 further includes the runtime environment 340 of the softwareproduct. In exemplary embodiments, the embedding of the content space atblock 326 occurs outside of the content space tool 110 as describedherein, and also occurs outside of the runtime environment 340 of thesoftware product. In exemplary embodiments, the runtime environment 340is as experienced by the customer that uses the product, in whateverhardware or device the software runs.

In exemplary embodiments, a content space is specified in a form that isprocessed (read) by the content space tool 110 (e.g., an agile userstory generation program). The specification can be split among multiplefiles (e.g., the content space specification files 105), which can beprocessed individually or together. As such, an overall product contentspace can be split among some number of individual architects forparallel concurrent activity, and then processed as a whole.

In exemplary embodiments, each content space specification file 105includes some number of noun spaces, defined symbols, and filters. Acontent space specification file 105 is used to define a content spacein a form that can be processed programmatically. In exemplaryembodiments, the specification file 105 is implemented to generate userstories and provide various kinds of statistics about the content space,enables content coverage metric, automated comparisons of multiplecontent spaces (e.g. cross-release), and the like. In exemplaryembodiments, the content space specification file 105 includes severalstatements, which define, among other things, a noun space, that caninclude noun, verb, interface (ifc) and platform. A content space is aset of noun spaces. As such, a basic content space specification filedefines one or more noun spaces. Descriptive names are used for thevalues on all these dimensions. In exemplary embodiments, additionalstatements can be added to the content space specification file 105. Onstatement is symbol (SYM) to simplify maintenance of the content spacespecification file 105 by reducing redundancy across noun spacedefinitions. Another statement is a filter statement that is used toclassify user stories, and to add information to output user stories. Inexemplary embodiments, each instance of statements as a group, defines asingle noun space. For example, the noun statement gives the noun spacea name, and the other verb, interface and platform statements providethe values for which each dimension is named.

As further described herein, a sym statement is a simple mechanism tocreate a short-hand for a list of values. The short-hand can then beused in defining noun spaces (e.g., in ‘noun’, ‘verb’, ‘ifc’, ‘platform’statements), in other sym statements, and in filter statements. Thisimplementation of sym statements therefore simplifies use and laterchanges to the content specification file since the list of relatedvalues can reliably changed throughout a set of specification files bychanging it in only a single place. For example, assume a content spacehas 15 noun spaces and 12 of those all use the same platform list. Thenthat list can defined once as a sym and that sym name used in the 12noun spaces. The example illustrates a group of related syms thataggregates various example platforms. The sym ‘all_email_env’ is thenused to in the definition of various noun spaces, for example in the‘draft email’ noun space.

The symbols that end in a trailing ‘_’ (underbar) are fold syms, as isthe ‘send_’. The ‘_’ indicates a symbol that can be folded. If therelevant type of value folding is requested (e.g. verb value to foldverb dimension, or platform value to fold platform dimension) then thesymbols marked with a trailing ‘_’ are folded. That is, the symbolitself is used in the content space when folded. If not folded thesymbol's value list is used in the content space. When folded a symbolis shown in generated user stories with the trailing ‘_’ so thateveryone seeing the user story will know it is folded (is anabstraction).

As further described herein, filter statements are used to classify userstories into one of five categories; n/a, future, nochange, changed ornew. They also can add to a story a variety of information. A filterstatement has the general structure: filter, <expression>,<classification>, <other requests>. The filter expression is a logicalexpression (i.e., evaluates to True or False) based on the language ofthe content the content space tool 110. For example, logical operatorsare supported (i.e., =, !=, >, <, in, not in, etc.) and the variablesallowed are ‘noun’, ‘verb’, ‘ifc’, ‘platform’ and defined symbols(sym's). Other keyword-value pairs which may be included in a filterstatement include but are not limited to: 1) Owner, owner name; 2) Groupor Group by request; 3) Priority, priority value; 3) Testid, testidvalue; and 4) Tag, list of tag values. By default, filtering is doneafter all the content space specification files 105 have been read andafter folding is performed. The content space tool 110 has an option toturn off all filtering which is useful at time to check the results ofcontent space changes.

In exemplary embodiments, the content space specification files 105 canimplement additional statements, including, but not limited to: 1)comment_off—used to end commented-out block of lines; 2) comment_on—usedto start a block of comment lines. Starts skipping; 3) createdby—used toset the field ‘Created By’; 4) csvfile—sets the name of the output .csvfile; 5) eof—logically ends file early (rest of file skipped); 6)include—name a file to be included; 7) planned for—used to set the RTCfield ‘Planned For’; 8) scope—used to set filter scope to file (default)or global; 9) set_filterid_in_summaryfield—true or false (default); 10)set_implicit_folding—true or false (default); 11)set_summary_prefix_—Default is “User Story”; 12)set_summary_suffix—Default is category of the user story; 13)tag_exclusion_set—Define a mutually exclusive set of tags; and 14)title—title (label) of content space.

As described herein, the specification files 105 support the definitionof symbols used in the defining the values and in the filters, that is,used within the content space specification file itself. This formathelps maintain a content space specification by lessening duplication ofconstants (i.e., dimension values). This format also serves to help thespecification file be self-documenting when description names are usedfor the symbols. For example, a list of platforms used in a priorrelease might be assigned to a symbol named ‘prior_platforms’. Thissymbol is then used in the noun spaces as a short-hand for the fulllist. This symbol can also be used in the filters.

Each use case in a content space is classified using filters into basiccategories including, but not limited to: not applicable, future,regression and development. “Not applicable” are use cases judged tolikely never be relevant for the product and future are use cases not inthe n+1 release but inherent in the content space. In exemplaryembodiments, the content space is identified to clearly encompass therequirements to help ensure nothing is missed. In doing so, some usecases are likely to be generated that are not planned for the currentrelease.

In exemplary embodiments, filters are also implemented to addinformation to the generated use cases. Examples of information that canbe added are priority, tags, references to requirements document and thelike.

In exemplary embodiments, filters are also implemented to cause sets ofuse cases to be grouped into a single, broader output use case.Implementing filters in this manner can be helpful in the caseregression use cases where fine-grained management and tracking of theindividual use cases is not necessary (e.g., due to the existence ofautomated testing built during previous releases).

In generating the agile use cases, one or more content spacespecification files 105 are read by the content space tool 110. Asdescribed herein, a primary output is the user story storage medium 115.In exemplary embodiments, the user story storage medium can have a commaseparated value (.csv) file format, which is a quasi-standard widelyused by many software applications. A second type of output is theadditional storage medium 120 for various summary and report likeinformation or in progress changes.

As described herein, content space data is logged and profiled andcoverage metrics are self-reported at block 330, which is now describedin further detail.

As described herein, the exemplary systems and methods support contentspace logging, profiling and self-reporting content coverage. Withrespect to logging, real time data related to actual user implementationin each software product, ties the functions implemented by the user tothe content space with a GUI. Feedback can then be generated into theGUI showing how each of the functions of the software product has beenused. In exemplary embodiments, the content space subdivides thesoftware product, which then enables collection of data and statisticsat runtime, which is mapped to the content space. With respect toprofiling, given a noun or any set of features of the content space, thesystems and methods described herein generate profile statistics forparticular use cases. Since the software product recognizes its owncontent space, the products injects real time and real world performancedata of the software product into the content space. With respect tocontent coverage, the systems and methods described herein measure thetest completeness of the software product. As described herein, sincethe software product recognizes its own content space, the softwareproduct can track the content space as the product is being used in realtime. As such, a user can inquire at any given time what part of thecode (being represented by a user story in the content space) and whatpercentage of the code is being utilized.

FIG. 4 illustrates a screen shot of a GUI 400 that can be implemented bya user to view and navigate content space data as described herein. Theexample in FIG. 4 illustrates an interactive tree-map, although it willbe appreciated that other user interfaces are contemplated in otherexemplary embodiments. The user can therefore generate reports as a treemap as a type of auditing. The example illustrates “server auditing”,although other names are contemplated. In exemplary embodiments, thetree-map on the example illustrates multiple named rectangles, eachrectangle sized relative to the number of user stories the rectanglecontains. In the example, the tree-map can include four levels. At thetop level (shown) each large rectangle corresponds to a product resourcewhich is familiar to the user as they work with the resources daily. Inexemplary embodiments, color dimensions can be implanted for variousimplementations, such as but not limited to relative frequency ofexecution of a particular cell of the content space.

In exemplary embodiments, the user can click on a rectangle and zoominto that resource and see all the functions associated with it.Clicking again shows all the platforms, and the fourth level show theinterfaces (GUI, CLI and REST). A right-click can zoom the tree-map upone level. At the leafs, the customer can click on various specificreports about that portions of the tree-map, which is a set of userstories. The user can then export the content space data and send it tothe software company for metrics analysis.

In exemplary embodiments, the GUI 400 can show a log file with messagesof user stories (Content Space coordinates) included. The user could usestandard table sorting/filtering to see only the Content Space messagesor only messages from a given story. As described herein, a user story(i.e., a region of the content space) is uniquely identified by itscoordinates. The user story is the set of coordinate values on fourdimensions for the story; noun, verb, interface, platform. (The fifthdimension of the content space is time, usually denoted by a productrelease and version. But for logging purposes the value on thisdimension is not needed in the output.) Following the convention ofcoordinate order, the following illustrates example user story labelingthat are supported in system or application logs (and in errormessages):

{Virtual Appliance, deploy to Server System Pool, GUI, PowerVM with VIOSNG} {Virtual Server, suspend, REST, VMware} {Virtual Server, restart, *,KVM with SAN} {Virtual Appliance, capture new version, *, ?}

In this example, “*” indicates all coordinate value for that dimension,and “?” indicates not known. In exemplary embodiments, the content spacecan be shipped with the software product and available for fixes andrelease updates like the rest of the product. A standard wrapper is usedso the product code can access the embedded user story information.

As described herein, the embedded content space can then be implemented(e.g., through the GUI 400 described with respect to FIG. 4) to log andprofile user information and to measure test completeness (i.e. coveragemetric self-reporting).

With regard to logging, the systems and methods described hereingenerate user stories that facilitate moving user story information inlogs and error messages to be used by customers and analysis, and movingprofile information for customer review. In exemplary embodiments, thesystems and methods described herein monitor and visualize user storydata for usage of a software product. The data can then be passed (e.g.,via the content space) on to a particular company for inclusion in theagile process without confidentiality concerns. As described herein, thesaved user story data can be in a form including but not limited to: alog file; a database and files. Regardless of the form, each formincludes timestamps or interval measurements, so that users can analyzenot only the frequency of each story, but also the mean time orcumulative time for each story. In this way the logging of the real timedata for the users provides information regarding what the users aredoing for a particular product, which ties the product function into thestructure of the content space (i.e., a particular function is a userstory). In turn, by implementing a GUI (e.g., the GUI 400 of FIG. 4),feedback can be entered showing how the data has been used. In exemplaryembodiments, the content space sub-divides a product at runtime andcollects the data and statistics, which are mapped to the content space.In addition, log entries are indexed by the content space.

The internal representation of a software product's own user stories(generated via a content space) provides an interface for internalaccess. The internal representation ships with the software product.When there is an error log entry associated with the software product,an error message or FFDC data is to be generated, and the content spacecoordinates for user stories relevant, are included with log or messagedata. The user story data is then included in the content space when itis sent to the respective company. In exemplary embodiments, this datais included in defects, as appropriate, for later analysis. In addition,for any given log entry, message, and the like, multiple user storiesmay be relevant and are supported in the content space.

With regard to profiling, the system and methods described hereincollect execution counts and duration data as execution occurs in thecustomer installation. This data is saved with associated indexes to mapit to user stories. In addition, the user can use a GUI (e.g., the GUI400 of FIG. 4) to view and perhaps export this data, and request andview analysis. In exemplary embodiments, given a noun or any set offeatures of the content space, the systems and methods described hereingenerate profile statistics for particular use cases. Since the softwareproduct recognizes its own content space, the products injects real timeand real world performance data of the software product into the contentspace. In exemplary embodiments, the content space sub-divides a productat runtime and collects the data and statistics, which are mapped to thecontent space. In addition, profile entries are indexed by the contentspace. In this way, when a user is implementing a software product, realtime and real world uses of a particular function of the product aremapped to user stories which are then stored in the content space. Assuch, not only is the content space used to store user stories relatedto a particular function of the product, but is also used to storeactual implementations of those functions as additional user stories.This real time and real world data is thus injected into the contentspace as performance data.

With respect to content coverage, the systems and methods describedherein measure the test completeness of the software product. Asdescribed herein, since the software product recognizes its own contentspace, the software product can track the content space as the productis being used in real time. As such, a user can inquire at any giventime what part of the code (being represented by a user story in thecontent space) and what percentage of the code is being utilized. Thesystems and method described herein reset parts of the profile data andextract the base data after tests have been executed, in order toself-report the data. The exported data allows direct calculation ofcontent coverage metrics with necessary splits.

As described herein, to log and profile user information and to measuretest completeness, the content space is embedded in the product whenshipped. In exemplary embodiments, the systems and methods describedherein embed a content space within a software product for availabilityfor normal use at run-time, thus allowing the logging, profiling andmetric coverage self-reporting described herein. In exemplaryembodiments, the systems and methods described herein implement acontent space represented internally, shippable and useable at run-time.In addition, the systems and methods described herein implement theinternal interface for the software product's internal functional partsto access the content space at run time (e.g., an internal callable setof interfaces that are used by product code). The systems and methodsdescribed herein further obtain and set attributes to each cell in thecontent space. The attributes are used for various purposes by therun-time functions access content space. Some example attributesinclude, but are not limited to: 1) cell category; 2) cell requirements;3) development owner; 4) test owner; 5) GUI panel ID; 6) instancesneeded, and the like. The systems and methods described herein furtherintegrate a run-time content space within a normal software productbuild process. In addition, the systems and methods described hereinupdate the content space definition within the software product afterthe software is installed (similar to updating other components of thesoftware product).

The content space logging and profiling, coverage metric self-reportingand other content space implementations described herein can beperformed in any suitable computing system as now described. FIG. 5illustrates an exemplary embodiment of a system 500 in which contentspace logging and profiling and coverage metric self-reporting can beimplemented. The methods described herein can be implemented in software(e.g., firmware), hardware, or a combination thereof. In exemplaryembodiments, the methods described herein are implemented in software,as an executable program, and is executed by a special orgeneral-purpose digital computer, such as a personal computer,workstation, minicomputer, or mainframe computer. The system 500therefore includes general-purpose computer 501.

In exemplary embodiments, in terms of hardware architecture, as shown inFIG. 5, the computer 501 includes a processor 505, memory 510 coupled toa memory controller 515, and one or more input and/or output (I/O)devices 540, 545 (or peripherals) that are communicatively coupled via alocal input/output controller 535. The input/output controller 535 canbe, but is not limited to, one or more buses or other wired or wirelessconnections, as is known in the art. The input/output controller 535 mayhave additional elements, which are omitted for simplicity, such ascontrollers, buffers (caches), drivers, repeaters, and receivers, toenable communications. Further, the local interface may include address,control, and/or data connections to enable appropriate communicationsamong the aforementioned components.

The processor 505 is a hardware device for executing software,particularly that stored in memory 510. The processor 505 can be anycustom made or commercially available processor, a central processingunit (CPU), an auxiliary processor among several processors associatedwith the computer 501, a semiconductor based microprocessor (in the formof a microchip or chip set), a macroprocessor, or generally any devicefor executing software instructions.

The memory 510 can include any one or combination of volatile memoryelements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM,etc.)) and nonvolatile memory elements (e.g., ROM, erasable programmableread only memory (EPROM), electronically erasable programmable read onlymemory (EEPROM), programmable read only memory (PROM), tape, compactdisc read only memory (CD-ROM), disk, diskette, cartridge, cassette orthe like, etc.). Moreover, the memory 510 may incorporate electronic,magnetic, optical, and/or other types of storage media. Note that thememory 510 can have a distributed architecture, where various componentsare situated remote from one another, but can be accessed by theprocessor 505.

The software in memory 510 may include one or more separate programs,each of which comprises an ordered listing of executable instructionsfor implementing logical functions. In the example of FIG. 5, thesoftware in the memory 510 includes the content space logging andprofiling and coverage metric self-reporting methods described herein inaccordance with exemplary embodiments and a suitable operating system(OS) 511. The OS 511 essentially controls the execution of othercomputer programs, such the content space logging and profiling andcoverage metric self-reporting systems and methods as described herein,and provides scheduling, input-output control, file and data management,memory management, and communication control and related services.

The content space logging and profiling and coverage metricself-reporting methods described herein may be in the form of a sourceprogram, executable program (object code), script, or any other entitycomprising a set of instructions to be performed. When a source program,then the program needs to be translated via a compiler, assembler,interpreter, or the like, which may or may not be included within thememory 510, so as to operate properly in connection with the OS 511.Furthermore, the content space logging and profiling and coverage metricself-reporting methods can be written as an object oriented programminglanguage, which has classes of data and methods, or a procedureprogramming language, which has routines, subroutines, and/or functions.

In exemplary embodiments, a conventional keyboard 550 and mouse 555 canbe coupled to the input/output controller 535. Other output devices suchas the I/O devices 540, 545 may include input devices, for example butnot limited to a printer, a scanner, microphone, and the like. Finally,the I/O devices 540, 545 may further include devices that communicateboth inputs and outputs, for instance but not limited to, a networkinterface card (NIC) or modulator/demodulator (for accessing otherfiles, devices, systems, or a network), a radio frequency (RF) or othertransceiver, a telephonic interface, a bridge, a router, and the like.The system 500 can further include a display controller 525 coupled to adisplay 530. In exemplary embodiments, the system 500 can furtherinclude a network interface 560 for coupling to a network 565. Thenetwork 565 can be an IP-based network for communication between thecomputer 501 and any external server, client and the like via abroadband connection. The network 565 transmits and receives databetween the computer 501 and external systems. In exemplary embodiments,network 565 can be a managed IP network administered by a serviceprovider. The network 565 may be implemented in a wireless fashion,e.g., using wireless protocols and technologies, such as WiFi, WiMax,etc. The network 565 can also be a packet-switched network such as alocal area network, wide area network, metropolitan area network,Internet network, or other similar type of network environment. Thenetwork 565 may be a fixed wireless network, a wireless local areanetwork (LAN), a wireless wide area network (WAN) a personal areanetwork (PAN), a virtual private network (VPN), intranet or othersuitable network system and includes equipment for receiving andtransmitting signals.

If the computer 501 is a PC, workstation, intelligent device or thelike, the software in the memory 510 may further include a basic inputoutput system (BIOS) (omitted for simplicity). The BIOS is a set ofessential software routines that initialize and test hardware atstartup, start the OS 511, and support the transfer of data among thehardware devices. The BIOS is stored in ROM so that the BIOS can beexecuted when the computer 501 is activated.

When the computer 501 is in operation, the processor 505 is configuredto execute software stored within the memory 510, to communicate data toand from the memory 510, and to generally control operations of thecomputer 501 pursuant to the software. The content space logging andprofiling and coverage metric self-reporting methods described hereinand the OS 511, in whole or in part, but typically the latter, are readby the processor 505, perhaps buffered within the processor 505, andthen executed.

When the systems and methods described herein are implemented insoftware, as is shown in FIG. 5, the methods can be stored on anycomputer readable medium, such as storage 520, for use by or inconnection with any computer related system or method.

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

In exemplary embodiments, where the content space logging and profilingand coverage metric self-reporting methods are implemented in hardware,the content space logging and profiling and coverage metricself-reporting methods described herein can implemented with any or acombination of the following technologies, which are each well known inthe art: a discrete logic circuit(s) having logic gates for implementinglogic functions upon data signals, an application specific integratedcircuit (ASIC) having appropriate combinational logic gates, aprogrammable gate array(s) (PGA), a field programmable gate array(FPGA), etc.

Technical effects include obtaining user story information in logs anderror messages to be implemented by service and defect analysis, andobtaining profile information mapped to user stories for analysis andavailable for customer review, which can include performance, usabilitycoverage metric and usage profile.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of onemore other features, integers, steps, operations, element components,and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated

The flow diagrams depicted herein are just one example. There may bemany variations to this diagram or the steps (or operations) describedtherein without departing from the spirit of the invention. Forinstance, the steps may be performed in a differing order or steps maybe added, deleted or modified. All of these variations are considered apart of the claimed invention.

While the preferred embodiment to the invention had been described, itwill be understood that those skilled in the art, both now and in thefuture, may make various improvements and enhancements which fall withinthe scope of the claims which follow. These claims should be construedto maintain the proper protection for the invention first described.

What is claimed is:
 1. A computer-implemented method for generating userstories for a software product, the method comprising: creating, by aprocessor, a plurality of content space specification files that eachinclude a plurality of requirements; processing, by the processor, theplurality of content space specification files to generate the userstories that are related to real time data of the software product;defining, by the processor, a content space for representing a portionof the software via a set of dimensions; mapping, by the processor, theuser stories to the content space; and traversing, by the processor, thecontent space to generate the user stories, wherein the content spaceincludes a plurality of cells, each of the plurality of cellscorresponding to one of the user stories, each of the plurality of cellshaving multiple dimensions, each of the multiple dimensions having oneor more values, the multiple dimensions including release, noun, verb,interface, and platform, wherein the verb, interface and platformdimensions are orthogonal and noun-specific; and embedding, by theprocessor, the content space with the software product, wherein duringexecution of the software product the content space is configured tostore user stories include at least one of real time log data, profilestatistics data, and coverage metric self-reporting data.
 2. Thecomputer-implemented method as claimed in claim 1 further comprisingoutputting, by the processor, the user stories.
 3. Thecomputer-implemented method as claimed in claim 1 wherein processing theplurality of content space specification files comprises identifyingcontent space specification statements in each of the plurality ofcontent space specification files.
 4. The computer-implemented method asclaimed in claim 1 wherein traversing the content space comprises: foreach of the noun dimensions, for each of the plurality of cells:traversing, by the processor, other dimensions of the multipledimensions of the cell, one value at a time, to generate the user storycorresponding to the cell.
 5. The computer-implemented method as claimedin claim 2 further comprising grouping, by the processor, the contentspace.
 6. The computer-implemented method as claimed in claim 2 furthercomprising folding, by the processor, the content space.
 7. A computerprogram product for generating user stories for a software product, thecomputer program product including a non-transitory computer readablemedium storing instructions for causing a computer to implement amethod, the method comprising: creating, a the processor, a plurality ofcontent space specification files that each include a plurality ofrequirements; processing, by the processor, the plurality of contentspace specification files to generate the user stories that are relatedto real time data of the software product; defining, by the processor, acontent space for representing a portion of the software via a set ofdimensions; traversing, by the processor, the content space to generatethe user stories, wherein the content space includes a plurality ofcells, each of the plurality of cells corresponding to one of the userstories, each of the plurality of cells having multiple dimensions, eachof the multiple dimensions having one or more values, the multipledimensions including release, noun, verb, interface, and platform,wherein the verb, interface and platform dimensions are orthogonal andnoun-specific; and mapping, by the processor, the user stories to thecontent space; and embedding, by the processor, the content space withthe software product, wherein during execution of the software productthe content space is configured to store user stories include at leastone of real time log data, profile statistics data, and coverage metricself-reporting data.
 8. The computer program product as claimed in claim7, wherein the method further comprises outputting the user stories. 9.The computer program product as claimed in claim 7 wherein processingthe plurality of content space specification files comprises identifyingcontent space specification statements in each of the plurality ofcontent space specification files.
 10. The computer program product asclaimed in claim 7 wherein traversing the content space comprises foreach of the noun dimensions, for each of the plurality of cells:traversing, by the processor, other dimensions of the multipledimensions of the cell, one value at a time, to generate the user storycorresponding to the cell.
 11. The computer program product as claimedin claim 8, wherein the method further comprises grouping the contentspace.
 12. The computer program product as claimed in claim 8, whereinthe method further comprises folding the content space.